PageSoft pagesoftwiki https://pagesoft.miraheze.org/wiki/Main_Page MediaWiki 1.41.0 first-letter Media Special Talk User User talk PageSoft PageSoft talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Module Module talk 0 1 1 2024-04-20T09:57:55Z MediaWiki default 1 Welcome to Miraheze! wikitext text/x-wiki __NOTOC__ == Welcome to {{SITENAME}}! == This Main Page was created automatically and it seems it hasn't been replaced yet. === For the bureaucrat(s) of this wiki === Hello, and welcome to your new wiki! Thank you for choosing Miraheze for the hosting of your wiki, we hope you will enjoy our hosting. You can immediately start working on your wiki or whenever you want. Need help? No problem! We will help you with your wiki as needed. To start, try checking out these helpful links: * [[mw:Special:MyLanguage/Help:Contents|MediaWiki guide]] (e.g. navigation, editing, deleting pages, blocking users) * [[meta:Special:MyLanguage/FAQ|Miraheze FAQ]] * [[meta:Special:MyLanguage/Request features|Request settings changes on your wiki]]. (Extensions, Skin and Logo/Favicon changes should be done through [[Special:ManageWiki]] on your wiki, see [[meta:Special:MyLanguage/ManageWiki|ManageWiki]] for more information.) ==== I still don't understand X! ==== Well, that's no problem. Even if something isn't explained in the documentation/FAQ, we are still happy to help you. You can find us here: * [[meta:Special:MyLanguage/Help center|On our own Miraheze wiki]] * On [[phorge:|Phorge]] * On [https://miraheze.org/discord Discord] * On IRC in #miraheze on irc.libera.chat ([irc://irc.libera.chat/%23miraheze direct link]; [https://web.libera.chat/?channel=#miraheze webchat]) === For visitors of this wiki === Hello, the default Main Page of this wiki (this page) has not yet been replaced by the bureaucrat(s) of this wiki. The bureaucrat(s) might still be working on a Main Page, so please check again later! 070d9e6457eab136df99905438a1f57c037772b0 2 1 2024-04-21T19:30:08Z Rextomasic 2 wikitext text/x-wiki __NOTOC__ == PageSoft Internal Wiki == This Main Page was created automatically and it seems it hasn't been replaced yet. === For the bureaucrat(s) of this wiki === Hello, and welcome to your new wiki! Thank you for choosing Miraheze for the hosting of your wiki, we hope you will enjoy our hosting. You can immediately start working on your wiki or whenever you want. Need help? No problem! We will help you with your wiki as needed. To start, try checking out these helpful links: * [[mw:Special:MyLanguage/Help:Contents|MediaWiki guide]] (e.g. navigation, editing, deleting pages, blocking users) * [[meta:Special:MyLanguage/FAQ|Miraheze FAQ]] * [[meta:Special:MyLanguage/Request features|Request settings changes on your wiki]]. (Extensions, Skin and Logo/Favicon changes should be done through [[Special:ManageWiki]] on your wiki, see [[meta:Special:MyLanguage/ManageWiki|ManageWiki]] for more information.) ==== I still don't understand X! ==== Well, that's no problem. Even if something isn't explained in the documentation/FAQ, we are still happy to help you. You can find us here: * [[meta:Special:MyLanguage/Help center|On our own Miraheze wiki]] * On [[phorge:|Phorge]] * On [https://miraheze.org/discord Discord] * On IRC in #miraheze on irc.libera.chat ([irc://irc.libera.chat/%23miraheze direct link]; [https://web.libera.chat/?channel=#miraheze webchat]) === For visitors of this wiki === Hello, the default Main Page of this wiki (this page) has not yet been replaced by the bureaucrat(s) of this wiki. The bureaucrat(s) might still be working on a Main Page, so please check again later! 24d8eed8c12e297e2bc013aa21a8d9b44604501a 3 2 2024-04-21T19:45:14Z Rextomasic 2 wikitext text/x-wiki __NOTOC__ '''Notice for site administrators:''' This wiki pertains to a fictional word processor program created to complete a school assignment. It has been created for '''non-commercial purposes'''. While the language implies that this is a real commercial product, it is to satisfy assignment requirements only. == PageSoft Internal Wiki == Welcome to the official PageSoft development wiki! This wiki aims to outline the overall product development project, along with the information development and content management project plan. ===Product Development Project=== *Main features *Bug fixes *Vision and goals *Scope *Schedule and milestones ==== Information Development and Content Management Project Plan ==== *Vision and goals *Scope *Content Map and Reuse Strategy *Project Assumptions *Schedule and milestones *Communication plan *DITA plan *Translation and localization plan *Roles and responsibilities *Dependencies and risks 09b971d374f8f1193071a6f32013ef44792f64bd 5 3 2024-04-21T20:00:46Z Rextomasic 2 /* Product Development Project */ wikitext text/x-wiki __NOTOC__ '''Notice for site administrators:''' This wiki pertains to a fictional word processor program created to complete a school assignment. It has been created for '''non-commercial purposes'''. While the language implies that this is a real commercial product, it is to satisfy assignment requirements only. == PageSoft Internal Wiki == Welcome to the official PageSoft development wiki! This wiki aims to outline the overall product development project, along with the information development and content management project plan. ===Product Development Project=== *[[Main features]] *Bug fixes *Vision and goals *Scope *Schedule and milestones ==== Information Development and Content Management Project Plan ==== *Vision and goals *Scope *Content Map and Reuse Strategy *Project Assumptions *Schedule and milestones *Communication plan *DITA plan *Translation and localization plan *Roles and responsibilities *Dependencies and risks b31b8d773e3b76aa76980c2af5523c373bd0d23f 6 5 2024-04-21T20:01:52Z Rextomasic 2 /* Product Development Project */ wikitext text/x-wiki __NOTOC__ '''Notice for site administrators:''' This wiki pertains to a fictional word processor program created to complete a school assignment. It has been created for '''non-commercial purposes'''. While the language implies that this is a real commercial product, it is to satisfy assignment requirements only. == PageSoft Internal Wiki == Welcome to the official PageSoft development wiki! This wiki aims to outline the overall product development project, along with the information development and content management project plan. ===Product Development Project=== *[[Main Features]] *Bug fixes *Vision and goals *Scope *Schedule and milestones ==== Information Development and Content Management Project Plan ==== *Vision and goals *Scope *Content Map and Reuse Strategy *Project Assumptions *Schedule and milestones *Communication plan *DITA plan *Translation and localization plan *Roles and responsibilities *Dependencies and risks 31848a1ed775d49a714d3a6991e8b395563a8c90 7 6 2024-04-21T20:09:27Z Rextomasic 2 /* Product Development Project */ wikitext text/x-wiki __NOTOC__ '''Notice for site administrators:''' This wiki pertains to a fictional word processor program created to complete a school assignment. It has been created for '''non-commercial purposes'''. While the language implies that this is a real commercial product, it is to satisfy assignment requirements only. == PageSoft Internal Wiki == Welcome to the official PageSoft development wiki! This wiki aims to outline the overall product development project, along with the information development and content management project plan. === Product Development Project === *[[Main Features]] *[[Bug Fixes]] *[[Vision and Goals (PDP)]] *[[Scope (PDP)]] *[[Schedule and Milestones (PDP)]] ==== Information Development and Content Management Project Plan ==== *[[Vision and Goals (IDP)]] *[[Scope (IDP)]] *[[Content Map and Reuse Strategy]] *[[Project Assumptions]] *[[Schedule and milestones (IDP)]] *[[Communication Plan]] *[[DITA Plan]] *[[Translation and Localization]] *[[Roles and Responsibilities]] *[[Dependencies and Risks]] 9039a3f03cc017a1034e906bace15dd33026df55 29 7 2024-04-21T22:37:18Z Rextomasic 2 /* PageSoft Internal Wiki */ wikitext text/x-wiki __NOTOC__ '''Notice for site administrators:''' This wiki pertains to a fictional word processor program created to complete a school assignment. It has been created for '''non-commercial purposes'''. While the language implies that this is a real commercial product, it is to satisfy assignment requirements only. == PageSoft Internal Wiki == Welcome to the official PageSoft development wiki! This wiki aims to outline the overall product development project, along with the information development and content management project plan. === Product Development Project === *[[Main Features]] *[[Bug Fixes]] *[[Vision and Goals (PDP)]] *[[Scope (PDP)]] *[[Schedule and Milestones (PDP)]] === Information Development and Content Management Project Plan === *[[Vision and Goals (IDP)]] *[[Scope (IDP)]] *[[Content Map and Reuse Strategy]] *[[Project Assumptions]] *[[Schedule and milestones (IDP)]] *[[Communication Plan]] *[[DITA Plan]] *[[Translation and Localization]] *[[Roles and Responsibilities]] *[[Dependencies and Risks]] === References === 7e97354c94a4d0724f9bfdd221c75f867907b146 30 29 2024-04-21T22:37:50Z Rextomasic 2 /* References */ wikitext text/x-wiki __NOTOC__ '''Notice for site administrators:''' This wiki pertains to a fictional word processor program created to complete a school assignment. It has been created for '''non-commercial purposes'''. While the language implies that this is a real commercial product, it is to satisfy assignment requirements only. == PageSoft Internal Wiki == Welcome to the official PageSoft development wiki! This wiki aims to outline the overall product development project, along with the information development and content management project plan. === Product Development Project === *[[Main Features]] *[[Bug Fixes]] *[[Vision and Goals (PDP)]] *[[Scope (PDP)]] *[[Schedule and Milestones (PDP)]] === Information Development and Content Management Project Plan === *[[Vision and Goals (IDP)]] *[[Scope (IDP)]] *[[Content Map and Reuse Strategy]] *[[Project Assumptions]] *[[Schedule and milestones (IDP)]] *[[Communication Plan]] *[[DITA Plan]] *[[Translation and Localization]] *[[Roles and Responsibilities]] *[[Dependencies and Risks]] === References === [[Reference List]] 33c2cc6f4ba64fdead81cedcf349514cc404d50b 36 30 2024-04-21T22:59:31Z Rextomasic 2 /* References */ wikitext text/x-wiki __NOTOC__ '''Notice for site administrators:''' This wiki pertains to a fictional word processor program created to complete a school assignment. It has been created for '''non-commercial purposes'''. While the language implies that this is a real commercial product, it is to satisfy assignment requirements only. == PageSoft Internal Wiki == Welcome to the official PageSoft development wiki! This wiki aims to outline the overall product development project, along with the information development and content management project plan. === Product Development Project === *[[Main Features]] *[[Bug Fixes]] *[[Vision and Goals (PDP)]] *[[Scope (PDP)]] *[[Schedule and Milestones (PDP)]] === Information Development and Content Management Project Plan === *[[Vision and Goals (IDP)]] *[[Scope (IDP)]] *[[Content Map and Reuse Strategy]] *[[Project Assumptions]] *[[Schedule and milestones (IDP)]] *[[Communication Plan]] *[[DITA Plan]] *[[Translation and Localization]] *[[Roles and Responsibilities]] *[[Dependencies and Risks]] === References === *[[Reference List]] ddeba461a3e4fc1dd4f28e8dadf464f4d30fb36f 0 2 4 2024-04-21T19:56:21Z Rextomasic 2 Created page with "The following features are being developed for PageSoft to improve the user experience. PageSoft aims to revolutionize word processors with these revolutionary features. == AI chatbot implementation == == AI enabled "simple English" translation == == Mobile to PC synchronization == According to market research, virtually all would-be PageSoft users possess a computer and smartphone that they use in their professional lives. While companies like Apple introduce synerg..." wikitext text/x-wiki The following features are being developed for PageSoft to improve the user experience. PageSoft aims to revolutionize word processors with these revolutionary features. == AI chatbot implementation == == AI enabled "simple English" translation == == Mobile to PC synchronization == According to market research, virtually all would-be PageSoft users possess a computer and smartphone that they use in their professional lives. While companies like Apple introduce synergy between these types of devices, this is limited to customers that have both an iPhone and iMac (Apple, 2024). PageSoft aims to bridge this gap for professionals, introducing seamless integration between mobile and desktop/laptop devices, regardless of manufacturer. This will make sending information, PageSoft drafts, and web media content a smoother experience that updates on both devices simultaneously. While most professionals opt to work on their computer, having a competent mobile alternative makes it easier to edit, adjust, and review documents on the fly. For this reason, special care will be given to seamlessly release mobile and computer versions of PageSoft. The mobile version will emphasize these tasks for users. Through Beta release user interviews, we have learned that mobile users have these quicker, simpler tasks in mind when utilizing mobile. Simple cloud architecture ensures that users can edit their files on any device to which they are signed in and see the changes across devices. For sharing of web content between mobile and computer, special care will be given to ensure users understand the differing integration of web content formatted on mobile versus computer. These differences can be very large and irreconcilable between formats. In essence, PageSoft aims to help users achieve higher levels of productivity by reducing the need to login to a computer for smaller changes on the go. == Embed social media and web content == ad463c57313abe8c5192c138afef9be78e7b9cad 37 4 2024-04-22T18:36:38Z Rextomasic 2 /* AI chatbot implementation */ wikitext text/x-wiki The following features are being developed for PageSoft to improve the user experience. PageSoft aims to revolutionize word processors with these revolutionary features. == AI chatbot implementation == The AI will be delivered through a chatbot screen parsed through industry text and translates that text into plain English. It’s a useful tool for the common laymen who need to understand in simple language the document or text they are reading. The lawyer's document that is full of legalese can now be parsed into a document anyone can understand. == AI enabled "simple English" translation == == Mobile to PC synchronization == According to market research, virtually all would-be PageSoft users possess a computer and smartphone that they use in their professional lives. While companies like Apple introduce synergy between these types of devices, this is limited to customers that have both an iPhone and iMac (Apple, 2024). PageSoft aims to bridge this gap for professionals, introducing seamless integration between mobile and desktop/laptop devices, regardless of manufacturer. This will make sending information, PageSoft drafts, and web media content a smoother experience that updates on both devices simultaneously. While most professionals opt to work on their computer, having a competent mobile alternative makes it easier to edit, adjust, and review documents on the fly. For this reason, special care will be given to seamlessly release mobile and computer versions of PageSoft. The mobile version will emphasize these tasks for users. Through Beta release user interviews, we have learned that mobile users have these quicker, simpler tasks in mind when utilizing mobile. Simple cloud architecture ensures that users can edit their files on any device to which they are signed in and see the changes across devices. For sharing of web content between mobile and computer, special care will be given to ensure users understand the differing integration of web content formatted on mobile versus computer. These differences can be very large and irreconcilable between formats. In essence, PageSoft aims to help users achieve higher levels of productivity by reducing the need to login to a computer for smaller changes on the go. == Embed social media and web content == b3e7d87a411584c1b2e461462fefded4c5aea143 38 37 2024-04-22T18:37:39Z Rextomasic 2 /* AI enabled "simple English" translation */ wikitext text/x-wiki The following features are being developed for PageSoft to improve the user experience. PageSoft aims to revolutionize word processors with these revolutionary features. == AI chatbot implementation == The AI will be delivered through a chatbot screen parsed through industry text and translates that text into plain English. It’s a useful tool for the common laymen who need to understand in simple language the document or text they are reading. The lawyer's document that is full of legalese can now be parsed into a document anyone can understand. == AI enabled "simple English" translation == PageSoft is a word processing company that requires future updates to stay abreast of the competion. This requires investment and engineering expertise. Although PageSoft has AI integrated currently it is only a grammar and spelling single AI. We are moving forward to a specialized one-of-a-kind AI that will turn Industry words into Plain English. We intend to do this by implementing a chatbot to help users with their plain English questions. To be more specific – when you are presented with the new housing diagrams for a renovation and those diagrams are full of words that you’re not familiar with our software will translate that into plain Plain English. == Mobile to PC synchronization == According to market research, virtually all would-be PageSoft users possess a computer and smartphone that they use in their professional lives. While companies like Apple introduce synergy between these types of devices, this is limited to customers that have both an iPhone and iMac (Apple, 2024). PageSoft aims to bridge this gap for professionals, introducing seamless integration between mobile and desktop/laptop devices, regardless of manufacturer. This will make sending information, PageSoft drafts, and web media content a smoother experience that updates on both devices simultaneously. While most professionals opt to work on their computer, having a competent mobile alternative makes it easier to edit, adjust, and review documents on the fly. For this reason, special care will be given to seamlessly release mobile and computer versions of PageSoft. The mobile version will emphasize these tasks for users. Through Beta release user interviews, we have learned that mobile users have these quicker, simpler tasks in mind when utilizing mobile. Simple cloud architecture ensures that users can edit their files on any device to which they are signed in and see the changes across devices. For sharing of web content between mobile and computer, special care will be given to ensure users understand the differing integration of web content formatted on mobile versus computer. These differences can be very large and irreconcilable between formats. In essence, PageSoft aims to help users achieve higher levels of productivity by reducing the need to login to a computer for smaller changes on the go. == Embed social media and web content == 668842a5f89ae06063a788b8aa6afb4711d229af 39 38 2024-04-22T18:39:02Z Rextomasic 2 /* Embed social media and web content */ wikitext text/x-wiki The following features are being developed for PageSoft to improve the user experience. PageSoft aims to revolutionize word processors with these revolutionary features. == AI chatbot implementation == The AI will be delivered through a chatbot screen parsed through industry text and translates that text into plain English. It’s a useful tool for the common laymen who need to understand in simple language the document or text they are reading. The lawyer's document that is full of legalese can now be parsed into a document anyone can understand. == AI enabled "simple English" translation == PageSoft is a word processing company that requires future updates to stay abreast of the competion. This requires investment and engineering expertise. Although PageSoft has AI integrated currently it is only a grammar and spelling single AI. We are moving forward to a specialized one-of-a-kind AI that will turn Industry words into Plain English. We intend to do this by implementing a chatbot to help users with their plain English questions. To be more specific – when you are presented with the new housing diagrams for a renovation and those diagrams are full of words that you’re not familiar with our software will translate that into plain Plain English. == Mobile to PC synchronization == According to market research, virtually all would-be PageSoft users possess a computer and smartphone that they use in their professional lives. While companies like Apple introduce synergy between these types of devices, this is limited to customers that have both an iPhone and iMac (Apple, 2024). PageSoft aims to bridge this gap for professionals, introducing seamless integration between mobile and desktop/laptop devices, regardless of manufacturer. This will make sending information, PageSoft drafts, and web media content a smoother experience that updates on both devices simultaneously. While most professionals opt to work on their computer, having a competent mobile alternative makes it easier to edit, adjust, and review documents on the fly. For this reason, special care will be given to seamlessly release mobile and computer versions of PageSoft. The mobile version will emphasize these tasks for users. Through Beta release user interviews, we have learned that mobile users have these quicker, simpler tasks in mind when utilizing mobile. Simple cloud architecture ensures that users can edit their files on any device to which they are signed in and see the changes across devices. For sharing of web content between mobile and computer, special care will be given to ensure users understand the differing integration of web content formatted on mobile versus computer. These differences can be very large and irreconcilable between formats. In essence, PageSoft aims to help users achieve higher levels of productivity by reducing the need to login to a computer for smaller changes on the go. == Embed social media and web content == In addition, it can easily embed and share content from social media and web pages. This way it becomes a versatile tool for people who want to keep up with the latest invention, product, or service in any industry. f6bc53e32c2d31761e5599f113eb906cddb901cd 40 39 2024-04-22T18:40:07Z Rextomasic 2 wikitext text/x-wiki The following features are being developed for PageSoft to improve the user experience. PageSoft aims to revolutionize word processors with these revolutionary features. == AI chatbot implementation == The AI will be delivered through a chatbot screen parsed through industry text and translates that text into plain English. It’s a useful tool for the common laymen who need to understand in simple language the document or text they are reading. The lawyer's document that is full of legalese can now be parsed into a document anyone can understand. == AI enabled "simple English" translation == PageSoft is a word processing company that requires future updates to stay abreast of the competion. This requires investment and engineering expertise. Although PageSoft has AI integrated currently it is only a grammar and spelling single AI. We are moving forward to a specialized one-of-a-kind AI that will turn Industry words into Plain English. We intend to do this by implementing a chatbot to help users with their plain English questions. To be more specific – when you are presented with the new housing diagrams for a renovation and those diagrams are full of words that you’re not familiar with our software will translate that into plain Plain English. It allows you to learn new subjects and take online courses that require more than a beginner's knowledge of the subject matter. For example, if you as a user who wants to take a course in geology there are industry terms that you won’t know. One term might be Abyssal Plain. Using PageSoft AI software and running that term through our chatbot it will come back with a plain English term very similar to this… deep ocean floor (usually 2 to 6km deep), generally flat apart from occasional volcanic mountains and mid-ocean ridges. (society, n.d.) == Mobile to PC synchronization == According to market research, virtually all would-be PageSoft users possess a computer and smartphone that they use in their professional lives. While companies like Apple introduce synergy between these types of devices, this is limited to customers that have both an iPhone and iMac (Apple, 2024). PageSoft aims to bridge this gap for professionals, introducing seamless integration between mobile and desktop/laptop devices, regardless of manufacturer. This will make sending information, PageSoft drafts, and web media content a smoother experience that updates on both devices simultaneously. While most professionals opt to work on their computer, having a competent mobile alternative makes it easier to edit, adjust, and review documents on the fly. For this reason, special care will be given to seamlessly release mobile and computer versions of PageSoft. The mobile version will emphasize these tasks for users. Through Beta release user interviews, we have learned that mobile users have these quicker, simpler tasks in mind when utilizing mobile. Simple cloud architecture ensures that users can edit their files on any device to which they are signed in and see the changes across devices. For sharing of web content between mobile and computer, special care will be given to ensure users understand the differing integration of web content formatted on mobile versus computer. These differences can be very large and irreconcilable between formats. In essence, PageSoft aims to help users achieve higher levels of productivity by reducing the need to login to a computer for smaller changes on the go. == Embed social media and web content == In addition, it can easily embed and share content from social media and web pages. This content will look just as it does in the browser and will stay up to date when connected to the internet. This way it becomes a versatile tool for people who want to keep up with the latest invention, product, or service in any industry. 0b0d7e73f2c3e48d9ec80b08580a20530e370533 0 3 8 2024-04-21T20:12:00Z Rextomasic 2 Created page with "Our software development team has faced the following bugs while implementing the near features introduced by PageSoft. == Improper AI interpretation of idioms and dialects == It is important to remember we have licensed the AI technology incorporated into PageSoft. This makes specific changes to the proprietary technology impossible directly. Any glaring issues with the service should be brought up directly with the service provider. This makes dealing with idiomatic..." wikitext text/x-wiki Our software development team has faced the following bugs while implementing the near features introduced by PageSoft. == Improper AI interpretation of idioms and dialects == It is important to remember we have licensed the AI technology incorporated into PageSoft. This makes specific changes to the proprietary technology impossible directly. Any glaring issues with the service should be brought up directly with the service provider. This makes dealing with idiomatic/dialectic issues rather difficult to address directly. To avoid issues, it is best to follow these tips: *Use plain, direct English when instructing the AI and providing input. *If necessary, defining the term to the AI has shown promising results in interpretation. *Providing additional context in idiomatic/dialectal use cases helps the AI correctly interpret meaning. Our programming team is experimenting with using the AI client software iteratively to achieve best results. This can be done by: #Providing the AI with the clearest possible input. #Using PageSoft’s built in grammar and spell-checking ability to diagnose issues with the AI output. #Using these problem areas as input for the AI with the intention of clarifying the section. #Repeating step 3 as necessary until a suitable output has been given that is clear of grammar and spelling flags. This process has mixed results and can further warp the original meaning further. The software development team is encouraged to continue refining this process and wielding the licensed AI to its fullest potential. == Formatting issues when importing web media == With PageSoft’s increased focus on seamless web media integration, there is a special interest in refining this import and integration process. It is crucial to remember our internal statistic show that 90% of all imported media comes from only 12 different websites. Therefore, focus should be directed on compatibility with these websites first and foremost. When importing interactive elements, it is crucial to correctly import and format the XML content to display what the user is trying to import. Seeing as how PageSoft’s parent company has a web browser application on the market, programmers are encouraged to use this proprietary code in formatting imported web media in PageSoft. Special care should be given to the option to automatically push web media updates within PageSoft documents. If a user wants to import a “like count” with their content, that data should be up to date. There should also be a clear delineation between online and offline mode for this reason. It is important for the user to know if the integrated media that has been downloaded is not up to date. Specific issues have been arising with: *Separating advertising content from user generated content on social media. *Retaining user settings and browser settings that affect the content seen in-browser vs. in PageSoft. *How the preexisting PageSoft content reacts when importing web content. To remedy these issues, special care should be given to flagging ad-based content. The software development team is again encouraged to refer to our proprietary internet browser software code in achieving this. Most browsers on the market allow for settings to be exported, thus this information should be downloaded into PageSoft to avoid discrepancies in the copying process. In dealing with the effects seen on preexisting content in the PageSoft document, similar conventions used in importing images, visual elements, graphs, charts, etc. should be employed. The user should also have “import options” made available similar to pasting options that can alter how the web media is integrated. The team should also offer a preview feature before importing. The import is data intensive and takes time. It is much more time consuming than pasting and hitting undo should the results not be desirable. Providing multiple previews based on the predicted import results will allow users to select a format at a glance. 2aacabc49928e74d30473834a76193676bd49ebe 0 4 9 2024-04-21T20:14:21Z Rextomasic 2 Created page with "PageSoft is a stand-alone software word program that gives the user the ability to identify acronyms, sentences, and words and then rewrite the document converting it into plain English. Using an AI (Artificial Intelligence) chatbot implementation for completing tasks allows the user to convert Industry words (buzzwords) that a layman can reasonably understand. Our goal is to help develop a level playing field for anyone interested in a DIY (do it yourself) approach to..." wikitext text/x-wiki PageSoft is a stand-alone software word program that gives the user the ability to identify acronyms, sentences, and words and then rewrite the document converting it into plain English. Using an AI (Artificial Intelligence) chatbot implementation for completing tasks allows the user to convert Industry words (buzzwords) that a layman can reasonably understand. Our goal is to help develop a level playing field for anyone interested in a DIY (do it yourself) approach to give them the tools to achieve their objective with little or no reliance on the industry “professional.” In this way, they can save money, and time and understand what is happening behind the cover of specific industry words created to confuse the consumer. We are currently in a growth stage and find that innovation is essential as we have more and more competition. Our development team is working on these innovations and troubleshooting two bugs discovered through our alpha testing program. We are happy to acknowledge that two of our innovations have been approved by our engineering development team. Our four innovations are as follows: *AI chatbot implementation for completing tasks. *AI-enabled “simple English” translation (e.g. simplified “legalese”) *Mobile-to-PC synchronization *Easily embed and share content from social media and web pages. We are very close to Beta testing all four innovations and look forward to a more competitive and productive product. Due to the additional functions and the subsequent problems our stakeholders have requested an updated plan. Which we are very happy to provide. In this plan they will be able to identify: *Project assumptions *Risk Management and mitigation. *Communications plan *Marketing *Milestones Please note financing is not included. 100059480432286f2aea3bb25d343188f0995ce6 0 5 10 2024-04-21T20:20:46Z Rextomasic 2 Created page with "We intend to change PageSoft in several new ways as discussed. More importantly, we will add AI (Artificial Intelligence) to our existing product line. This is the most exciting announcement we will make for our stakeholders for this third quarter ever. It’s our game changer in this category and all stakeholders will benefit. We will license it from a third party, however, the community seems willing to outsource their code. Which allows us to move forward in many wa..." wikitext text/x-wiki We intend to change PageSoft in several new ways as discussed. More importantly, we will add AI (Artificial Intelligence) to our existing product line. This is the most exciting announcement we will make for our stakeholders for this third quarter ever. It’s our game changer in this category and all stakeholders will benefit. We will license it from a third party, however, the community seems willing to outsource their code. Which allows us to move forward in many ways. The source code will become public shortly which creates a proprietary problem for us. We will deal with that possible account if it comes under our project assumptions at the time – if any. For our stakeholders, we will be able to apply our software across the globe - fully licensed. It allows our narrow silo of the English language to expand to other multiple countries. When AI gets better so do we. As the world-leading word-processing software company, we dominate the market – unfortunately, we have multiple word-processing software companies at our doorstep looking to cut into our business. Therefore we need to stand up and take notice. When the applications that we are developing come to market it will change the entire playing field. And we will be the first to market making us the dominant player in the field. Being the first never means you as a company will lead. It only means you will be copied unless you have proprietary content – which we don’t. We will deal with this in our risk management section along with our mitigation plans which can be seen in the full content management plan. Dealing with open source AI anyone can become your competitor. We are the leading word- processing company in the world. Our innovations have helped individuals and companies throughout the world. We have a solid reputation which means a great deal to our customers – this is not to be underestimated or undervalued. We have serviced and supported the entire working public with strong bug-free software that has always backed its product for years. As a result, our stock shares reflect this. With these four innovations, we expect a rise in our shares with these new features. For stakeholders, this is good news. Our predictions with the total layout of all four innovations will increase our stock value by 22.5% This is a very generous ROI. And is 6.07% higher than any other stock on the market. 709d30008474c4f8c3e0ea73bd24bf5de804fbe4 0 6 11 2024-04-21T20:27:38Z Rextomasic 2 Created page with "{| class="wikitable" |+ Caption text |- ! Date !! Goal/Milestone !! Notes |- | March 2022 || Board meeting to discuss the engineering department proposal to include suggested new updates || Vote taken 73% voted in favor of adopting the proposal |- | April 2022 || Example || Example |- | May 2022 || Example || Example |- | August 2022 || Example || Example |- | October 2022 || Example || Example |- | June 2023 || Example || Example |- | November 2023 || Example || Example..." wikitext text/x-wiki {| class="wikitable" |+ Caption text |- ! Date !! Goal/Milestone !! Notes |- | March 2022 || Board meeting to discuss the engineering department proposal to include suggested new updates || Vote taken 73% voted in favor of adopting the proposal |- | April 2022 || Example || Example |- | May 2022 || Example || Example |- | August 2022 || Example || Example |- | October 2022 || Example || Example |- | June 2023 || Example || Example |- | November 2023 || Example || Example |- | December 2023 || Example || Example |- | March 2023 || Example || Example |- | October 2023 || Example || Example |- | November 2023 || Example || Example |- | March 2024 || Example || Example |- | May 2024 || Example || Example |- | August 2024 || Example || Example |} 5166dd1f2359ed9bfeb9086f67f9c37182e66908 12 11 2024-04-21T21:09:18Z Rextomasic 2 wikitext text/x-wiki {| class="wikitable" |+ Product Development Project: Schedule and Milestones |- ! Date !! Goal/Milestone !! Notes |- | April 2022 || PageSoft project proposal approved by executives. || |- | July 2022 || Key stakeholder meetings complete. Planning begins. || |- | August 2022 || Scope of project submitted and finalized. || |- | September 2022 || First round of user interviews and research take place. || |- | October 2022 || Project goals and timeline finalized for development phase. || |- | November 2022 || Software development team begins development. || |- | June 2023 || Alphas build released for quality assurance. || Feedback introduced changed development goals/deadlines. |- | December 2023 || Beta build released to quality assurance team and Beta testers. || Bugs and issues identified to be addressed in final build. |- | January 2024 || Second round of user interviews conducted with Beta build. || |- | May 2024 || Updated software due for submission. || Includes bug fixes and new features. |- | October 2024 || Final program, documentation materials, and marketing materials completed. || This includes localized materials. |- | November 2024 || Production process for initial version begins. || |- | December 2024 || Delivery of PageSoft to customers. || |} 93f45f9dbe5ecd1cd82cf860a2f5d3d153321cf3 0 7 13 2024-04-21T21:17:43Z Rextomasic 2 Created page with "== Vision and goals == The information development team is tacking this project with a unified content strategy (Rockley and Cooper, 2012). This will involve an automated reuse strategy powered by DITA to publish documentation in various forms: *PDFs *Web content *E-learning content *Marketing brochures *Embedded help files By having an information development team member present in the daily Agile scrums held by the software development team, we can stay abreast of p..." wikitext text/x-wiki == Vision and goals == The information development team is tacking this project with a unified content strategy (Rockley and Cooper, 2012). This will involve an automated reuse strategy powered by DITA to publish documentation in various forms: *PDFs *Web content *E-learning content *Marketing brochures *Embedded help files By having an information development team member present in the daily Agile scrums held by the software development team, we can stay abreast of product development project changes. This means mitigating the impact of change to work efficiently, meet deadlines, and have our work finished and available for translation and localization as early as possible. 44af25834019ae6850b700b97ac61056b09a6e44 0 8 14 2024-04-21T21:27:48Z Rextomasic 2 Created page with "== Scope == PageSoft aims to be an evolution of typical Word processors. This means taking what has worked for previous word processors — the workspace, creation tools, editing tools, design conventions, and such — and focusing our sights on the new features promised by the program. Similarly, our information development plan will aim to assist with these new features as seamlessly as possible while retaining help information on traditional features. Much of the he..." wikitext text/x-wiki == Scope == PageSoft aims to be an evolution of typical Word processors. This means taking what has worked for previous word processors — the workspace, creation tools, editing tools, design conventions, and such — and focusing our sights on the new features promised by the program. Similarly, our information development plan will aim to assist with these new features as seamlessly as possible while retaining help information on traditional features. Much of the help content from previous word processors created by the parent company can be used here, further shifting our focus onto new features. The quality assurance (testing) team has provided us with user feedback from the Beta build. By working with the software development team as changes occur (via our scrum participant), we can gauge the most significant concerns and queries PageSoft users will have regarding using the new features correctly and to their fullest potential. Using DITA, according to our '''DITA process''', to tag all content we produce means tracking this information and keeping it up to date with the software development team’s changes. Using our DITA tool and communicating effectively in a remote environment will allow the project to progress without issue. 02377f0a4359d88611033d7daebf39db103ea0bc 32 14 2024-04-21T22:49:05Z Rextomasic 2 wikitext text/x-wiki == Scope == PageSoft aims to be an evolution of typical Word processors. This means taking what has worked for previous word processors — the workspace, creation tools, editing tools, design conventions, and such — and focusing our sights on the new features promised by the program. Similarly, our information development plan will aim to assist with these new features as seamlessly as possible while retaining help information on traditional features. Much of the help content from previous word processors created by the parent company can be used here, further shifting our focus onto new features. The quality assurance (testing) team has provided us with user feedback from the Beta build. By working with the software development team as changes occur (via our scrum participant), we can gauge the most significant concerns and queries PageSoft users will have regarding using the new features correctly and to their fullest potential. Using DITA, according to our [[DITA Plan]], to tag all content we produce means tracking this information and keeping it up to date with the software development team’s changes. Using our DITA tool and communicating effectively in a remote environment will allow the project to progress without issue. a35d201275ed82c23231227275eb16f4893d9738 0 9 15 2024-04-21T21:36:07Z Rextomasic 2 Created page with "== Content Map == {| class="wikitable" |+ Content used in each documentation format |- ! User PDF Instructions !! Embedded Help !! Web Content !! Marketing Brochures !! e-Learning Materials |- | Overview || Instruction || Overview || Overview || Overview |- | New Features || FAQ || New Features || New Features || New Features |- | Instruction || Tips for Best Use || Instruction || Sales Pitch || Instruction |- | FAQ || Links to Web Content || FAQ || Animated Demonstratio..." wikitext text/x-wiki == Content Map == {| class="wikitable" |+ Content used in each documentation format |- ! User PDF Instructions !! Embedded Help !! Web Content !! Marketing Brochures !! e-Learning Materials |- | Overview || Instruction || Overview || Overview || Overview |- | New Features || FAQ || New Features || New Features || New Features |- | Instruction || Tips for Best Use || Instruction || Sales Pitch || Instruction |- | FAQ || Links to Web Content || FAQ || Animated Demonstrations || FAQ |- | Tips for Best Use || Animated Demonstrations || Tips for Best Use || || Tips for Best Use |- | || || Animated Demonstrations|| || Animated Demonstrations |- | Example || Example || Example || Example || Example |- | || || Sales Pitch|| || Links to Web Content |} 230b54d8e5a67a991946cc27a00a2e07b187cf58 16 15 2024-04-21T21:36:48Z Rextomasic 2 /* Content Map */ wikitext text/x-wiki == Content Map == {| class="wikitable" |+ Content used in each documentation format |- ! User PDF Instructions !! Embedded Help !! Web Content !! Marketing Brochures !! e-Learning Materials |- | Overview || Instruction || Overview || Overview || Overview |- | New Features || FAQ || New Features || New Features || New Features |- | Instruction || Tips for Best Use || Instruction || Sales Pitch || Instruction |- | FAQ || Links to Web Content || FAQ || Animated Demonstrations || FAQ |- | Tips for Best Use || Animated Demonstrations || Tips for Best Use || || Tips for Best Use |- | || || Animated Demonstrations|| || Animated Demonstrations |- | || || Sales Pitch|| || Links to Web Content |} 9e4953d353ff1b82434a320fba98fc2fdd4f6b17 18 16 2024-04-21T21:40:41Z Rextomasic 2 wikitext text/x-wiki == Content Map == {| class="wikitable" |+ Content used in each documentation format |- ! User PDF Instructions !! Embedded Help !! Web Content !! Marketing Brochures !! e-Learning Materials |- | Overview || Instruction || Overview || Overview || Overview |- | New Features || FAQ || New Features || New Features || New Features |- | Instruction || Tips for Best Use || Instruction || Sales Pitch || Instruction |- | FAQ || Links to Web Content || FAQ || Animated Demonstrations || FAQ |- | Tips for Best Use || Animated Demonstrations || Tips for Best Use || || Tips for Best Use |- | || || Animated Demonstrations|| || Animated Demonstrations |- | || || Sales Pitch|| || Links to Web Content |} [[File:Content Map Final Proj.png|thumb|This diagram illustrates the flow of information from raw development information into usable output for documentation powered by DITA.]] 847bf32fb39ba4846f347e284ace4d3297dcd7b3 19 18 2024-04-21T21:42:25Z Rextomasic 2 wikitext text/x-wiki == Content Map == {| class="wikitable" |+ Content used in each documentation format |- ! User PDF Instructions !! Embedded Help !! Web Content !! Marketing Brochures !! e-Learning Materials |- | Overview || Instruction || Overview || Overview || Overview |- | New Features || FAQ || New Features || New Features || New Features |- | Instruction || Tips for Best Use || Instruction || Sales Pitch || Instruction |- | FAQ || Links to Web Content || FAQ || Animated Demonstrations || FAQ |- | Tips for Best Use || Animated Demonstrations || Tips for Best Use || || Tips for Best Use |- | || || Animated Demonstrations|| || Animated Demonstrations |- | || || Sales Pitch|| || Links to Web Content |} [[File:Content Map Final Proj.png|thumb|This diagram illustrates the flow of information from raw development information into usable output for documentation powered by DITA.]] == Reuse Strategy == The information development project has opted to employ an automated reuse strategy. This will be achieved using the DITA and content management tools available within Adobe FrameMaker. Adopting an automated reuse strategy has various advantages. Firstly, it will work seamlessly with our DITA architecture and toolset. Structured DITA content is tagged and updated which is ideal for automated reuse. This can be done on the level of components, fragments, and sections of information. Secondly, it will assist with change mitigation. Automated reuse ensures all use cases of any given structured DITA content are automatically updated. The nature of DITA ensures derivative reuse will be seamless and painless (Rockley and Cooper, 2012). Thirdly, it fits well into the goals of the overall product development project by simplifying the flow of information through the software development team, to the information development team, and into use in various materials and departments. This includes the marketing, translation, and localization teams, along with executives and other stakeholders. This can be visualized in the content map. Reuse itself will be done in component, fragment, and section varieties. This ensures that DITA content, along with its meaningful organization, can be preserved with sectional reuse between materials, as outlined in the content map. This will highly reduce the amount of time spent organizing our structured DITA content between use cases. An appropriate granularity ensures that sectional reuse is feasible (Rockley and Cooper, 2012). Given our focus on developing informational content for the new features introduced by PageSoft, effective fragment reuse will be crucial as well. This is easily achieved with an appropriately tagged series of structured DITA content. The highly granular nature of each DITA component means information will remain up-to-date amid changes. Sticking with granular DITA components makes the translation and localization process easier by allowing for the appropriate teams to organize structured content as they see fit. It avoids relying on verbose, possibly out of date copy that has is harder to adapt. b058a8cfdb364254bf9c0367c2d09f3c3cea6006 6 10 17 2024-04-21T21:40:13Z Rextomasic 2 wikitext text/x-wiki Content Map for the information development project in PageSoft (fictional). 2b65238fe1c8eddfcfb4a57196e65d9f0fb9e051 0 11 20 2024-04-21T21:45:22Z Rextomasic 2 Created page with "We have made the following assumptions regarding the rollout of our new features. *We will hire outside contractors to create the databases for the majority of these industries *We are assuming there will be enough contractors to hire *The bug fixes will be problem-solved within the allotted time *We do not anticipate any new evolving bugs" wikitext text/x-wiki We have made the following assumptions regarding the rollout of our new features. *We will hire outside contractors to create the databases for the majority of these industries *We are assuming there will be enough contractors to hire *The bug fixes will be problem-solved within the allotted time *We do not anticipate any new evolving bugs f25e8b9a5a32e8b04e4e2e3e8fbfde561788af29 0 12 21 2024-04-21T21:55:38Z Rextomasic 2 Created page with "{| class="wikitable" |+ Information Development Project Schedule and Milestones |- ! Date !! Goal/Milestone !! Notes |- | March 2022 || Board meeting to discuss the engineering department proposal to include suggested new updates || Vote taken 73% voted in favor of adopting the proposal |- | April 2022 || Key Stakeholder meeting || 86% of stakeholders vote to move the project forward -update is requested |- | May 2022 || Financing is budgeted. Agile methodology is adopte..." wikitext text/x-wiki {| class="wikitable" |+ Information Development Project Schedule and Milestones |- ! Date !! Goal/Milestone !! Notes |- | March 2022 || Board meeting to discuss the engineering department proposal to include suggested new updates || Vote taken 73% voted in favor of adopting the proposal |- | April 2022 || Key Stakeholder meeting || 86% of stakeholders vote to move the project forward -update is requested |- | May 2022 || Financing is budgeted. Agile methodology is adopted for the entire project || Sprints are implemented for management |- | August 2022 || Authority to start work is given || |- | October 2022 || Phase 1 meeting with development team || Positive feedback and outlook |- | June 2023 || Phase 2 meeting with development team || Plan tweaking |- | November 2023 || Phase 3 meeting with development team || Bugs identified in alpha testing |- | December 2023 || Phase 4 meeting with development team || Bugs are fixed and product is ready for Beta testing |- | March 2023 || Communication/Marketing plan is developed with ad agency || |- | October 2023 || Marketing is complete and ready for rollout || |- | November 2023 || Marketing plan is executed || |- | March 2024 || Marketing plan analytics examined || Did not perform as predictions indicated |- | May 2024 || Tweaked marketing plan and second rollout begins || |- | August 2024 || Marketing plan is a success || Marketing plan is a success |} 0667dbe05f88b983a3995189aa36b1310347dbb9 0 13 22 2024-04-21T21:57:57Z Rextomasic 2 Created page with "Our software is a communications product – we pioneered it and trail-blazed for many companies after us. We are universally used throughout the world and have been the number 1 used word-processing company for many years. Why do we need to communicate that? It’s very simple. Our product is well used and well known. However, how many people know about AI? Most have heard about it in the news but don’t realize we and many more companies use it as a form of it seam..." wikitext text/x-wiki Our software is a communications product – we pioneered it and trail-blazed for many companies after us. We are universally used throughout the world and have been the number 1 used word-processing company for many years. Why do we need to communicate that? It’s very simple. Our product is well used and well known. However, how many people know about AI? Most have heard about it in the news but don’t realize we and many more companies use it as a form of it seamlessly in our products already. Those silent grammar suggestions or spelling mistakes are all tagged and brought to the attention of our users. Although these are standard features now throughout the industry we cannot rely on our laurels. Innovation must continue and this is our answer. This product is different. It offers an opportunity to tag paragraphs of text and have it rewritten by our integrated AI. If the document is full of industry words you tag the document and ask the AI to simplify. Or you can ask it to please rewrite this document at a grade 6 level. It all depends on the language and needs of the user. For example, if it’s a legal document full of legalese you can ask the AI to describe all terms and conditions in the document in plain understandable English. It will create something that you the layman can understand and talk to your lawyer about any concerns or at the very least understand what he/she is saying. dbc9ec957a06bc07762e3fcaa5ca01737548bcd4 6 14 23 2024-04-21T22:20:22Z Rextomasic 2 wikitext text/x-wiki A Map of DITA reuse (fictional project). 3efcbb1668eb1fddac3e14440956ca5644255a3b 0 15 24 2024-04-21T22:23:49Z Rextomasic 2 Created page with "Our DITA tool of choice for this project will be Adobe FrameMaker. Conveniently, this program is already used in the structuring and publishing of our technical documentation. On top of these features, the program contains excellent DITA authoring tools (Adobe, 2024). The use of DITA content in relation to the product development cycle can be visualized in the content map. The role of DITA content in our reuse strategy can be found in detail here. In essence, our DITA..." wikitext text/x-wiki Our DITA tool of choice for this project will be Adobe FrameMaker. Conveniently, this program is already used in the structuring and publishing of our technical documentation. On top of these features, the program contains excellent DITA authoring tools (Adobe, 2024). The use of DITA content in relation to the product development cycle can be visualized in the content map. The role of DITA content in our reuse strategy can be found in detail here. In essence, our DITA tool is used to create DITA content. This content should be highly granular, containing a single statement, fact, or value. By tagging this content with metadata, we can do multiple things: *Track changes that have been made in the lifecycle of the content. *Referencing to automatically change sections that use the DITA content as said content is updated. *Conditionalizing sets of DITA content that permit fragment and sectional reuse (Rockley and Cooper, 2012). *Filtering DITA content based on conditions (e.g. Mobile vs. computer versions of PageSoft). The flow of information can be seen in the attached process map. [[File:DITA ProcessMap.png|thumb|This process map shows the flow of information of the information development project and the role DITA plays in automated reuse.]] As our team receives raw development information, '''DITA content is manually created''' with appropriate tagging. This DITA content is then used to '''manually structure documentation''' that '''automatically reuses DITA content'''. When our team inevitably receives updated raw development information, the DITA components are '''manually edited''' to reflect these changes, '''automatically producing current and up-to-date DITA content'''. The edited content is '''automatically changed''' in documentation use cases as well. c7f6852aac2507033cfcc05b125262847ced8a45 33 24 2024-04-21T22:54:20Z Rextomasic 2 wikitext text/x-wiki Our DITA tool of choice for this project will be Adobe FrameMaker. Conveniently, this program is already used in the structuring and publishing of our technical documentation. On top of these features, the program contains excellent DITA authoring tools (Adobe, 2024). The use of DITA content in relation to the product development cycle can be visualized in the [[Content Map and Reuse Strategy|content map]]. The role of DITA content in our [[Content Map and Reuse Strategy|reuse strategy]] can be found in detail here. In essence, our DITA tool is used to create DITA content. This content should be highly granular, containing a single statement, fact, or value. By tagging this content with metadata, we can do multiple things: *Track changes that have been made in the lifecycle of the content. *Referencing to automatically change sections that use the DITA content as said content is updated. *Conditionalizing sets of DITA content that permit fragment and sectional reuse (Rockley and Cooper, 2012). *Filtering DITA content based on conditions (e.g. Mobile vs. computer versions of PageSoft). The flow of information can be seen in the attached process map. [[File:DITA ProcessMap.png|thumb|This process map shows the flow of information of the information development project and the role DITA plays in automated reuse.]] As our team receives raw development information, '''DITA content is manually created''' with appropriate tagging. This DITA content is then used to '''manually structure documentation''' that '''automatically reuses DITA content'''. When our team inevitably receives updated raw development information, the DITA components are '''manually edited''' to reflect these changes, '''automatically producing current and up-to-date DITA content'''. The edited content is '''automatically changed''' in documentation use cases as well. da2788c2c4da88eaab53216b9867b4208ac0bb59 0 16 25 2024-04-21T22:27:17Z Rextomasic 2 Created page with "The content produced by our information development team will be translated and localized by outside service providers contracted by our parent company. This will aim to localize the product in three Asian markets; namely China, India, and Japan. For this undertaking, a contract has been made with “translations.com”, which offers a software localization service (translations.com, 2016). As shown in the Schedule and Milestones for the product development project, we..." wikitext text/x-wiki The content produced by our information development team will be translated and localized by outside service providers contracted by our parent company. This will aim to localize the product in three Asian markets; namely China, India, and Japan. For this undertaking, a contract has been made with “translations.com”, which offers a software localization service (translations.com, 2016). As shown in the Schedule and Milestones for the product development project, we aim to have our finalized documentation ready for translation and localization by the software submission deadline in May 2024. Talks with their localization teams confirmed that they will also be using DITA tools to author their documentation. For this reason, it is crucial that we provide them with our final documentation, along with the DITA components oh high granularity we produced in the process. Similarly, simple and direct language should be used when authoring documentation as this is better for both English users and the translation team. While the localization team will also be ensuring cultural appropriateness in our documentation, special care should be given to avoid culturally specific references and jargon that would muddle the information. Keep analogies global and inoffensive. 868f16ebb5f7d1510d6c7882c9a2c281e5a0d736 34 25 2024-04-21T22:55:37Z Rextomasic 2 wikitext text/x-wiki The content produced by our information development team will be translated and localized by outside service providers contracted by our parent company. This will aim to localize the product in three Asian markets; namely China, India, and Japan. For this undertaking, a contract has been made with “translations.com”, which offers a software localization service (translations.com, 2016). As shown in the [[Schedule and Milestones (PDP)|schedule and milestones]] for the product development project, we aim to have our finalized documentation ready for translation and localization by the software submission deadline in May 2024. Talks with their localization teams confirmed that they will also be using DITA tools to author their documentation. For this reason, it is crucial that we provide them with our final documentation, along with the DITA components oh high granularity we produced in the process. Similarly, simple and direct language should be used when authoring documentation as this is better for both English users and the translation team. While the localization team will also be ensuring cultural appropriateness in our documentation, special care should be given to avoid culturally specific references and jargon that would muddle the information. Keep analogies global and inoffensive. 09b2fe6e55a7ed6ba2f66575a3c9c7be4712dd89 0 17 26 2024-04-21T22:30:22Z Rextomasic 2 Created page with "Various roles and responsibilities will fall to members of the information development team. This includes a team member that will sit in on all software development Agile scrum meetings." wikitext text/x-wiki Various roles and responsibilities will fall to members of the information development team. This includes a team member that will sit in on all software development Agile scrum meetings. b617fba0df73ad9694b7a5e5b8128465f14c4215 6 18 27 2024-04-21T22:35:21Z Rextomasic 2 wikitext text/x-wiki PageSoft risks (fictional) 0970e421d664fec7ebb71e754d191a847d4928e3 0 19 28 2024-04-21T22:36:18Z Rextomasic 2 Created page with "To mitigate the impact of change on the project, the automated reuse strategy powered by the DITA toolset ensures we can stay abreast of changes to the PageSoft development as they happen. The following risks are being accounted as outlined in the attached image. [[File:Harrison Risk Table.png|thumb|The following product development project risks should be considered as well.]] Several potential risks are associated with developing new software using third-party AI plug..." wikitext text/x-wiki To mitigate the impact of change on the project, the automated reuse strategy powered by the DITA toolset ensures we can stay abreast of changes to the PageSoft development as they happen. The following risks are being accounted as outlined in the attached image. [[File:Harrison Risk Table.png|thumb|The following product development project risks should be considered as well.]] Several potential risks are associated with developing new software using third-party AI plugins. PageSoft would have to depend on the quality of the AI and the company supplying it. There would be a risk that the AI would not integrate with our software or worse it would cause our software not to function properly. 1a3c4ef58eff5fa504d9283978477a21be9ac0f4 35 28 2024-04-21T22:57:33Z Rextomasic 2 wikitext text/x-wiki To mitigate the impact of change on the project, the automated [[Content Map and Reuse Strategy|reuse strategy]] powered by the [[DITA Plan|DITA plan]] and tools ensures we can stay abreast of changes to the PageSoft development as they happen. The following risks are being accounted as outlined in the attached image. [[File:Harrison Risk Table.png|thumb|The following product development project risks should be considered as well.]] Several potential risks are associated with developing new software using third-party AI plugins. PageSoft would have to depend on the quality of the AI and the company supplying it. There would be a risk that the AI would not integrate with our software or worse it would cause our software not to function properly. f3fe23b24c47bcea2794c92edf1605dac04e264b 0 20 31 2024-04-21T22:38:49Z Rextomasic 2 Created page with "Apple (2024). Intro to syncing your Mac and your devices. Apple Support. https://support.apple.com/en-ca/guide/mac-help/mchl923c1147/mac Adobe FrameMaker - XML/DITA Editor. (2024). Www.adobe.com. Retrieved March 13, 2024, from https://www.adobe.com/ca/products/framemaker/xml-dita-editor.html Rockley, A., & Cooper, C. (2012). Managing Enterprise Content: A Unified Content Strategy. New Riders. Seguin, Christine. (2024, January 16). 24W_TWR2014_450 Course Content. Algon..." wikitext text/x-wiki Apple (2024). Intro to syncing your Mac and your devices. Apple Support. https://support.apple.com/en-ca/guide/mac-help/mchl923c1147/mac Adobe FrameMaker - XML/DITA Editor. (2024). Www.adobe.com. Retrieved March 13, 2024, from https://www.adobe.com/ca/products/framemaker/xml-dita-editor.html Rockley, A., & Cooper, C. (2012). Managing Enterprise Content: A Unified Content Strategy. New Riders. Seguin, Christine. (2024, January 16). 24W_TWR2014_450 Course Content. Algonquin University. https://brightspace.algonquincollege.com/d2l/le/content/621312/Home Translation.com. Software Localization & Testing. (2016, December 1). Www.translations.com. https://www.translations.com/services/language-services/software-localization.html#Overview Winter, J. (n.d.). Council Post: Unified Content Strategy, An Introduction. Forbes. Retrieved February 8, 2024, from https://www.forbes.com/sites/forbestechcouncil/2018/05/29/unified-content-strategy-an-introduction/?sh=7ccdd486367e 10b16bf4fca582df46fe5f987a80b3377b2b6b84